Not sure why inlining changes the behavior of the parser,
but `_top_level` has to be inlined, otherwise everything breaks.

- Remove `type_clause` rule
- Remove `type_parameter_list` aliases
- Update and organize tests for type definitions
- Add query patterns for `where_expression` and subtyping operators

- Simplify `signature` definition
- Remove `return_type` and `where_clause` hacks

- Arrow functions cannot contain open tuples, so they should only allow
  closed assignments (like `let_statement`).
- Rename `function_expression` to `arrow_function_expression`.

Parse the start of block_comment as a regular token.

Parse the start of a string as a regular token, and then parse the
content of the string using the external tokenizer. This requires rules
for all types of content (string/command, normal/raw, single/triple),
but it doesn't require using the external tokenizer to serialize string
delimiters.

- Remove unnecessary newlines from `_comprehension_clause` and
  `matrix_expression`.
- Update definition of `_terminator`.

Co-authored-by: Imran Khan <[email protected]>

- Rename `addDots` to `addDot`.
- Move `token` call to `addDot` definition.

- Add `public_statement`
- Split import rule into `import_statement` and `using_statement`

All types of content are aliased as content. Query patterns will usually
need to include the parent rule anyways.

Since the alias only includes content tokenized by the scanner, escape
sequences are _not_ included.

Co-authored-by: MichaelHatherly <[email protected]>

Inside raw strings, only escaped delimiters and \\ are considered escape
sequences. Other backslashes are treated as regular characters.

tree-sitter 0.24.3